feat(git): add date-based commit log retrieval functions#2057
Merged
domdomegg merged 36 commits intomodelcontextprotocol:mainfrom Aug 25, 2025
Merged
feat(git): add date-based commit log retrieval functions#2057domdomegg merged 36 commits intomodelcontextprotocol:mainfrom
domdomegg merged 36 commits intomodelcontextprotocol:mainfrom
Conversation
added 2 commits
June 9, 2025 21:49
Add git_log_date_range and git_log_by_date functions to retrieve commits within a date range or for a specific date. Includes corresponding models and tool definitions for API integration.
Add git_log_date_range and git_log_by_date functions to retrieve commits within a date range or for a specific date. This enables users to filter commit history by date, which is useful for auditing and reporting purposes.
Contributor
Author
|
@olaservo can you take a look please? |
olaservo
added
server-git
Adding the Microsoft Docs MCP server github repo and description to the servers list.
Would like to move MS Docs MCP Server link and description up to official integrations. This is a server officially supported by Microsoft with canonical Microsoft product documentation hosted on learn.microsoft.com.
Add Alpaca’s official MCP server to community servers list
- Add head/tail functionality for memory-efficient file reading - Implement new list_directory_with_sizes command with file size info - Add formatSize utility for human-readable file sizes
Signed-off-by: rithin-pullela-aws <rithinp@amazon.com>
Signed-off-by: rithin-pullela-aws <rithinp@amazon.com>
…Berg-it/servers into feature/add-git-date-tools-docs
…e/add-git-date-tools-docs
Implemented functionality to retrieve branch information based on specified criteria, enhancing the Git tools available in the server. This includes support for local and remote branches, as well as filtering by commit containment.
…reamline commit history retrieval options.
domdomegg
requested changes
Aug 17, 2025
Member
domdomegg
left a comment
domdomegg
left a comment
There was a problem hiding this comment.
Could we instead add these as parameters to git_log? I think we just need start_timestamp and end_timestamp, as a model could pass in the start and end of a day to get a particular day.
Replace separate date range log functions with timestamp parameters in git_log Remove deprecated GitLogDateRange and GitLogByDate classes and tools
Contributor
Author
|
@domdomegg The requested updates are done. Please proceed with the review. |
Remove separate git_log_date_range and git_log_by_date functions as their functionality is now included in git_log with optional timestamp parameters
domdomegg
reviewed
Aug 23, 2025
src/git/src/mcp_server_git/server.py
Outdated
| max_count: int = 10 | ||
| start_timestamp: Optional[str] = Field( | ||
| None, | ||
| description="Start timestamp for filtering commits (ISO format or git-compatible date string)" |
Member
There was a problem hiding this comment.
ISO format or git-compatible date string
I think it would be good to be more explicit about a strict format here.
And also from the implementation, I don't think this looks true? (i.e. args.extend(['--format=%H%n%an%n%ad%n%s%n']) requires a certain format). Might have misunderstood though.
Contributor
Author
There was a problem hiding this comment.
@domdomegg For args.extend(['--format=%H%n%an%n%ad%n%s%n']): This line of code defines the output format for the git log command when date filtering is used. I’ve added more details to the description.
added 2 commits
August 25, 2025 15:04
Clarify supported timestamp formats in field descriptions by listing specific examples of ISO 8601, relative and absolute date formats
Member
nice! |
domdomegg
approved these changes
Aug 25, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Enhanced the git_log function to support date-based filtering with optional start_timestamp and end_timestamp parameters. This enables users to filter commit history by date ranges or specific time periods, which is useful for auditing and reporting purposes
Motivation and Context
These changes align with the project's focus on providing granular Git history analysis tools while maintaining backward compatibility with existing integrations
How Has This Been Tested?
Tested with Trae IDE
Breaking Changes
Types of changes
Checklist
Additional context